-
Notifications
You must be signed in to change notification settings - Fork 3
chore: migrated to package manager to pnpm #204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 51df6e3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This is even showing errors that does not show with npm.
|
I didn't experience that when I cloned and installed the repo. Would it help if we just regenerated the What version of |
Already did. Same version. With pnpm another issue appeared through the CI, and were not showing before with npm. Clearly pnpm are working properly where npm was not.
|
…replace-package-manager
And more.
|
Can you review? In some fixes, you should consider the comments I made. It's related. |
I would like for you to create an issue for the NPM issue which prompted you to want to migrate to PNPM in the first place, I'm fairly certain we could fix that without migrating package manager. Some of the issues you're seeing might come from:
|
https://pnpm.io/cli/recursive#--no-sort Weird that you do not prefer better tooling. As one can easily replace one for another, if ever needed. I gave the reasons in the PR. Not looking to resolve the issues in the current, but actual improve while resolving some that I mentioned. pnpm are clearly more functional than npm. |
I answered your reviews done in here. I have updated the first description post, it should be more clear. In my experience, pnpm (or yarn if not possible) and biome are minimum in a project. If after all the information provided, it's stil not enough, it's a waste, but feel free to close the PR. |
Another issue appeared here. Build from ferric were not being generated. I then removed But now the error are this one. And nothing to fix.
Then again, I installed with pnpm. It found the errors I mentioned in this PR with babel, where before with npm they dont even appear.
Wow, and the build now works with pnpm. |
Are you saying that regenerating the lockfile led to npm working for you? |
No, with that, it made it worse, it resulted in the error mentioned. Currently, I am using pnpm as workaround without commiting it, to be able to properly run the project. |
I removed the checks, as previous mentioned in the review, where I had added to prevent the fails, but there are different errors happening, not sure what the approach to fix them. |
Before I had trouble using
npm i
in the root, ferric-cli were not running, it wasnt finding the js.Even if it were recognized in the package-lock as workspace installed.
It only worked after I did a
pnpm i
straight in the ferric folder, then I was able to run the command standalone. That's the experience I had.This led to this PR. Which in fact work now just after a
pnpm install
in the root folder.pnpm
are faster, in my experience, there is no reason to not migrate to it, even more if fromnpm
.https://pnpm.io/pnpm-vs-npm
https://refine.dev/blog/pnpm-vs-npm-and-yarn/ - Faster CI installs and more